feat(eif): embed os-release into rpm2eif rootfs - #720
Draft
jmt-lab wants to merge 1 commit into
Draft
Conversation
jmt-lab
changed the title
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 12, 2026 23:59
35a170c to
3e75c59
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 13, 2026 20:14
3e75c59 to
0a2e52c
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 13, 2026 20:22
0a2e52c to
bc43ba5
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 13, 2026 20:31
bc43ba5 to
2051e91
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 13, 2026 22:59
2051e91 to
8397761
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 14, 2026 00:03
8397761 to
5effc29
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 14, 2026 20:40
5effc29 to
5907e91
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 14, 2026 21:21
5907e91 to
2fcb188
Compare
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 14, 2026 21:24
2fcb188 to
bd053c6
Compare
Mirror the os-release append that rpm2img performs, so EIF-built rootfs
images expose the same identifying fields (VERSION, PRETTY_NAME,
VARIANT_ID, VERSION_ID, BUILD_ID, VENDOR_NAME, and the canonical URLs)
to userspace. Unlike rpm2img, INSTALL_ROOT already points at the merged
sysroot, so the append writes directly to ${INSTALL_ROOT}/usr/lib/os-release
without the ${ARCH}-bottlerocket-linux-gnu/sys-root prefix.
jmt-lab
force-pushed
the
feat/eif-signing-07-os-release
branch
from
August 14, 2026 22:12
bd053c6 to
eed4c7c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirror the os-release append that rpm2img performs, so EIF-built rootfs
images expose the same identifying fields (VERSION, PRETTY_NAME,
VARIANT_ID, VERSION_ID, BUILD_ID, VENDOR_NAME, and the canonical URLs)
to userspace. Unlike rpm2img, INSTALL_ROOT already points at the merged
sysroot, so the append writes directly to ${INSTALL_ROOT}/usr/lib/os-release
without the ${ARCH}-bottlerocket-linux-gnu/sys-root prefix.